On Non-Functional Requirements in Software Engineering
نویسندگان
چکیده
Essentially a software system’s utility is determined by both its functionality and its non-functional characteristics, such as usability, flexibility, performance, interoperability and security. Nonetheless, there has been a lop-sided emphasis in the functionality of the software, even though the functionality is not useful or usable without the necessary non-functional characteristics. In this chapter, we review the state of the art on the treatment of non-functional requirements (hereafter, NFRs), while providing some prospects for future
منابع مشابه
Mapping Activity Diagram to Petri Net: Application of Markov Theory for Analyzing Non-Functional Parameters
The quality of an architectural design of a software system has a great influence on achieving non-functional requirements of a system. A regular software development project is often influenced by non-functional factors such as the customers' expectations about the performance and reliability of the software as well as the reduction of underlying risks. The evaluation of non-functional paramet...
متن کاملSupporting Requirements Traceability with Rationale
Requirements, both functional and non-functional, are the driving force behind the many decisions required to develop a software system. These decisions, alternative solutions, and the reasons behind them, can be captured in the rationale for the software system. The rationale contains the arguments for and against each alternative solution, which in turn relate to the functional and nonfunctio...
متن کاملFunctional & Non-Functional Requirement Elicitation and Risk Assessment for Agile Processes
Requirement analyses have a deep impact on software engineering. Requirement as the initial phase in the software development is a continuous client-centric process for the successful Agile software implementation. System Requirements for implementation are classified as Functional and Non-functional requirement. This paper represents different Function and Non-functional requirement elicitatio...
متن کاملTowards Modeling Non-Functional Requirements in Software Architecture
Functional requirements (FRs) capture the intended behavior of the system, in terms of the services or tasks the system is required to perform, while non-functional requirements (NFRs) are requirements that impose restrictions on the product being developed [3]. Despite the obvious importance and relevance of non-functional requirements, NFRs specified during requirement engineering are almost ...
متن کاملTowards the Proper Integration of Extra-Functional Requirements
In spite of the many achievements in software engineering, proper treatment of extra-functional requirements (also known as non-functional requirements) within the software development process is still a challenge to our discipline. The application of functionality-biased software development methodologies can lead to major contradictions in the joint modelling of functional and extra-functiona...
متن کاملAspect IPM: Towards an Incremental Process Model Based on AOP for Component-Based Systems
In spite of recent and constant researches in the Component-Based Development area, there is still a lack for patterns, processes and methodologies that effectively support either the development “for reuse” and “with reuse”. This paper presents Aspect IPM, a process model that integrates the concepts of component-based software engineering, frameworks, patterns, non-functional requirements and...
متن کاملذخیره در منابع من
با ذخیره ی این منبع در منابع من، دسترسی به آن را برای استفاده های بعدی آسان تر کنید
عنوان ژورنال:
دوره شماره
صفحات -
تاریخ انتشار 2009